Clear the 22 red test files on main and add the edition 18 lineage entry - #7

… children see PATH stubs

… constructor name

…w instead of dropping its observation

… file fallback

bin/test/no-argv-secrets.test.mjs read a secret written to a child's stdin
(lib/update/token.mjs, security -i) as shell interpolation because the
template sat on the same line as exec(. Stdin is the remedy the gate itself
names; spawn input payloads are now removed before matching, and a control
test proves the stdin form passes and the command-string form still fails.

monitor/mcp-tools-probe.mjs speak() wrote the three RPC frames with no stdin
error handler, so a server that exited before reading crashed the probe with
an unhandled EPIPE (CI ubuntu Node 22). EPIPE and ECONNRESET on stdin are now
expected; the exit handler gives the verdict. The race did not reproduce
locally: the new speak() test guards the exit verdict, not the race.

…s holding unread pipe data

On a refusal the helper SIGKILLs bwrap. If bwrap had not yet read the
resolv.conf written to fd 5, the helper's socketpair end failed with
ECONNRESET, which nothing handled: the helper crashed with exit 1 and a
stack, and a caller read the lane as failed instead of not run. This is the
intermittent bin/test/sandbox-netns-live.test.mjs:138 failure (1 !== 125)
seen on PRs #5 and #8. Pipe errors after a kill are now expected; any other
pipe error is a refusal. bin/test/sandbox-net-refusal-pipes.test.mjs
reproduces it with a fake bwrap that never reads fd 5: 0/15 before, 15/15
after.

…'s own shutdown deadlock skips instead of failing

The stress test's only control allocated objects, which never exercises the
background compile that deadlocks at natural exit (nodejs/node#54918, open).
macOS CI then failed intermittently on the renderer, which already exits
naturally and cannot exit more naturally than a control does. A second
control runs hot integer loops over a 1200x630x3 buffer and deflateSync at
level 9 with none of the renderer's code. If Node hangs either control, the
run skips and names the counts; process.exit() regressions are still caught
by the static exitHazards test on every run. Locally (Linux, 2 cores, Node
22.23) both controls hang: 13/24 and 17/24.

macOS Node 26 suite runs take 22-25 minutes; a run on 2026-11-12 was cancelled
at the 30-minute limit with every test it had reached passing.